home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dr. Windows 3
/
dr win3.zip
/
dr win3
/
VISUALBA
/
DFVB19.ZIP
/
DFRAMEVB.HIS
< prev
next >
Wrap
Text File
|
1994-03-09
|
37KB
|
828 lines
HISTORY FILE FOR DOORFRAME VBDOS
================================
DOORFRAME is now supported by Richard Paquette and Chuck Valecek.
Richard Paquette at: The Livewire BBS
Public Nodes (2) call > 609-235-5297 HST (Ring Down)
Private Nodes Not published until registered
Chuck Valecek at : Suburban Software BBS
Public Nodes (2) call > 708-636-6694
> 708-636-6697
Private Nodes Not Published until registered
Version 1.9
-----------
(12-10-93)
With this version you MUST overwrite the dframex.inc file.. it WILL NOT
work properly without this INC file overwritten.. YOU BEEN WARNED!
Changed most of the integer varibales to long integers, hopefully
this will stop some of those overflow problems using DOOR.SYS.
Added another routine called IN.KEY. This routine emulates the BASIC Inkey
command. You create a DO loop, call IN.KEY and watch the RESPONSE$ variable
for something other than a NULL.
Version 1.8
-----------
(06-28-93)
This was the last version compiled by Ted Freeman..
-> He died on July 13th 1993 <-
Well, looks like DoorFrame has finally grown to big for it's britches!
Wondered how long it would take with all the new stuff I've been adding.
Have had reports of String Space Corrupt errors which means it's time to
trim it down a bit. Consequently I had to decide what to discard. It was
a hard decision but I decided to drop support for WWIV's CHAIN.TXT file.
This will probably upset a few people but I tried to pick something that
would affect the least amount of systems.
Again, DOORFRAME NO LONGER SUPPORTS WWIV AND CHAIN.TXT.
(06-25-93)
Changed the way ENTER operates. Previously, it would accept any keystroke
and go on it's merry way. It now must actually receive an Enter key. This
change was made mainly for PCBoard/M. Although DoorFrame works flawlessly
with the vast majority of the systems running the M version, I have had a
couple of reports that on a few systems they are still getting 4 or 5
random characters at the start of the door. By using the ENTER subroutine
at the bottom of your opening screen, it should catch any extraneous
characters that should happen to pop up at the beginning (up to 80).
Added another variable (like we NEED another one!). Check4RIP% lets you
the programmer decide if you want to check for RIPscrip compatibility.
Obviously if your door doesn't send RIPscrip codes, you could care less
if the remote is RIP compatible or not. The default for Check4RIP% is 0
which does not check. If you do want to check for RIPscrip, populate the
variable with a non-zero value. You must assign this variable before calling
Detect.Ansi.
Version 1.7
-----------
(06-17-93)
DoorFrame will now recognize RIPscrip! There are two new variables
available, Rip% and Rip$. Rip% will be 0 if RIPscrip was not detected and
1 if it was. Rip$ will contain the RIPscrip version number in the format
RIPSCRIPxxyyzz where xx = major version number, yy = minor version number
and zz = revision code. For example if the version number is v1.52.00
Rip$ would contain RIPSCRIP015200.
The Graphics% variable is not adjusted in response to the presence or
absence of RIPscrip.
Version 1.6
-----------
(06-13-93)
Finally got this sucker to work with the PCBoard/M version! Although I
have no way of testing, it should also work with the Wildcat! IM software.
Maybe some of you Wildcatters can shoot me some feedback on whether it
does or not.
There is a trade-off involved (naturally!). I still can't figure out
where the *'s are coming from so the only solution I could come up with was
to ignore any *'s. So if you have any In.Put statements that require an *
as a response, you will have to change it. This only applies when the /FD
(fossil driver) parameter is being used. When no fossil is being used, the
* is accepted like always.
Version 1.5
-----------
(04-21-93)
Added the RIP color switch for Wildcat! systems. Color is now displayed if
either GR or RIP is detected in the Wildcat! DOOR.SYS file.
(04-20-93)
When adding the addtional colors for the shadow in the Box.It routine, I
neglected to allow for Black as a color! Therefore, 0 now indicates a Black
shadow and -1 indicates no shadow is to be used.
(04-18-93)
Added the Cipher routines from the PBClone library. These two routines
(Cipher and CipherP) allow simple text encryption/decryption with password
protection. Check the PBC-SUBS.DOC file for instructions on their use.
(04-16-93)
Added the ClearBuffer routine. This routine allows you to clear either
the keyboard buffer, the communications input buffer, or both. Parameters
are: 0 = Clear both, 1 = Clear comm. input only, 2 = Clear keyboard only.
(04-13-93)
Added another parameter to the SendAnsi routine. The third parameter is
Inter% and indicates whether or not to disable the ability to interrupt
the ANSI file with the spacebar as it is displaying. 0 = Don't disable,
1 = Disable. The default is 0.
(03-29-93)
Added support for PCBoard v15.0 Alias name. I added this because the
ALIAS$ variable was already in DoorFrame. I will not be adding the rest of
the new stuff from v15.0 as that would needlessly inflate the size of the
library to support only one system. (so don't ask!)
Version 1.4
-----------
(03-25-93)
Well my tweaking of the DETECT.ANSI routine didn't work quite the way it
was intended to! Consequently it is back to the way it was before.
(03-24-93)
When using the Box.It routine, you may now specify a background color to
be used for the Shadow% parameter. 0 = No Shadow, 1 - 7 = Background Color
for the Shadow.
(03-20-93)
Fixed a problem with clearing the screen on the local display when in
ASCII only mode.
(03-14-93)
Tweaked the DETECT.ANSI routine a bit. Hopefully it will do away with
those non-ANSI messages when ANSI is actually there!
Version 1.3
-----------
(02-25-93)
Well of course I had to screw something up when expanding the COM port
range! This only affected the DORINFOx.DEF systems but any COM port above
one got changed back to 1 which would usually result in a carrier lost
message.
(02-09-93)
Finally got around to expanding the COM port range. DoorFrame now supports
COM 0 thru 15.
Version 1.2
-----------
(01-12-93)
Silly me! When checking for the fossil driver parameter I neglected to put
the / in there. So it was checking for FD instead of /FD. That means if your
.CFG filename contained those 2 letters (as in dFDdemo!), it would pick that
up as the fossil parameter. Corrected now.
(01-07-93)
That old problem with the time expired when the Display was toggled off
in PCBoard popped up again! Fixed one more time (gotta quit changing things).
(01-03-93)
Removed the CLRSCRN during the INTIALIZE process so now clearing the
screen is up to you at the beginning of the door.
(12-23-92)
Fixed a stupid error on my part in the SENDANSI routine. I was opening the
file as FIL but was closing FILE! So the open file handles would just stack
up everytime the routine was called.
(12-12-92)
Added a new routine called SendAnsi. This routine is for true ANSI files
only! It sends the entire file non-stop. Pressing the Spacebar aborts the
file send. See the .DOC file for an explanation of accepted parameters.
Version 1.1
-----------
(11-24-92)
Noticed that I had only allowed for a single digit when specifying a
non-standard IRQ. That has been changed to accept 2 digits.
(11-19-92)
DoorFrame will now recognize the %pcbnode% and %wcnodeid% environment
variables when reading the path to the system file (1st line of the .CFG).
Some examples:
PCBoard: If USERS.SYS is located in C:\PCB\NODE1 directory,
%pcbdrive%%pcbdir%\NODE%pcbnode%\USERS.SYS
Wildcat!: USERINFO.DAT located in C